Delete Tool
Used to delete a tool from your project. This permanently removes the tool and all its associated configuration, actions, and settings.
API Endpoint
| Property | Value |
|---|---|
| Request Method | DELETE |
| Request URL | https://api.seliseblocks.com/tools/{tool_id} |
Request
Request Example
curl -X DELETE 'https://api.seliseblocks.com/tools/{tool_id}?project_key=YOUR_PROJECT_KEY' \
-H 'accept: application/json'
Path Parameters
| Field | Type | Required | Description |
|---|---|---|---|
| tool_id | string | Yes | The unique identifier of the tool to delete. |
Query Parameters
| Field | Type | Required | Description |
|---|---|---|---|
| project_key | string | No | The project key for your project. |
Request Headers
| Field | Type | Required | Description |
|---|---|---|---|
| accept | string | Yes | Accepted response format. Use application/json |
warning
Permanent Deletion Warning
- This operation permanently deletes the tool and cannot be undone
- All tool configuration, actions, and settings will be removed
- Any AI agents using this tool will no longer be able to access it
- Version history and usage statistics will be permanently lost
- Active integrations using this tool may fail after deletion
tip
Before deleting a tool:
- Export or backup tool configuration if you may need it later
- Check which AI agents are using this tool
- Review dependencies and integrations
- Consider setting the tool status to "inactive" instead of deleting
- Notify team members who may be using the tool
- Update documentation to reflect the removal
After successful deletion:
- Remove references to the tool from AI agent configurations
- Update any external integrations
- Document the deletion for audit purposes
- Clear any cached tool data in your applications
Response
Success Response (204 No Content)
Returns an empty response with status code 204 indicating successful deletion.
Status Code: 204 No Content
Response Body: Empty (no content)
note
A 204 status code indicates the tool was successfully deleted. Unlike other endpoints, this response does not include a JSON body. The absence of an error response confirms the deletion was completed.
Error Response (422 Unprocessable Entity)
Returns validation error details when the request parameters are invalid.
{
"detail": [
{
"loc": [
"path",
"tool_id"
],
"msg": "tool not found or already deleted",
"type": "value_error.notfound"
}
]
}
Error Response Fields
| Field | Type | Description |
|---|---|---|
| detail | array | Array of validation error objects. |
| loc | array | Location of the error in the request (e.g., path, query). |
| msg | string | Human-readable error message. |
| type | string | Error type identifier. |
Common Error Scenarios
| Error Type | Description | Resolution |
|---|---|---|
| Tool Not Found | Tool ID doesn't exist or was already deleted | Verify the tool_id is correct |
| Permission Denied | User lacks permission to delete the tool | Check user permissions in project settings |
| Tool In Use | Tool is currently being used by active agents | Stop agent executions or remove tool from agents first |
| Invalid Tool ID | Tool ID format is invalid | Ensure tool_id matches the expected format |
Error Codes
| Status Code | Description | Response Type |
|---|---|---|
| 204 | No Content - Tool deleted successfully | Success (Empty) |
| 400 | Bad Request - Invalid request | Bad Request |
| 403 | Forbidden - Insufficient permissions | Forbidden |
| 404 | Not Found - Tool does not exist | Not Found |
| 409 | Conflict - Tool is in use and cannot be deleted | Conflict |
| 422 | Validation Error - Invalid request parameters | Unprocessable Entity |